docs(roadmap): verify and correct #434 sub-item status#442
Merged
Conversation
Sub-items (b)-(f) of ROADMAP #434 hadn't been updated since the row was written, even though (b) and (c) shipped in v1.84.0. Corrected all five against verified evidence rather than re-asserting stale text: - (b)/(c): confirmed DONE via current hook/skill content and git history - (d): was built once as ROADMAP #195, kept as valuable in the v1.69.0 bloat audit, then deleted 2026-07-06 as unfired — only the failure-signal half of the original scope ever existed - (e): hooks/token-spike-check.sh (#220) does adjacent but distinct post-hoc anomaly detection, not the live cap-aware monitor (d) asked for - (f): today's sibling sync issues (claude-gdlc-wizard#15, claude-rdlc-wizard#10) are tracking only — neither repo has changed Codex (GPT-5.6 Sol, xhigh) reviewed 3 rounds to CERTIFIED, catching a wrong CHANGELOG citation and two overstated absence claims along the way. ROADMAP #434
BaseInfinity
added a commit
that referenced
this pull request
Jul 15, 2026
…net 5 medium default (#448) Catch-up release: seven consumer-affecting commits were stranded on main since v1.86.0 (July 5) because nothing prompts the manual tag-to-publish step — most urgently #445, the Copilot CLI argument-hint fix from the repo's first external contributor (@thejesh23), which npm consumers were not receiving. - CHANGELOG [1.87.0]: leads with the first-external-contribution credit; covers #441 (GPT-5.6 Sol reviewer sweep), #443 (Sonnet 5 medium default, unbacked 5x quota claim removed, hook floor), #445/#447 (Copilot fix + regression test), #446 (Setup A semantics), #440/#442 (chores) - Version bumps at all sites found by the broad grep (v1.85.0 lesson) - ROADMAP #448 (Copilot CLI compat watch) + #449 (release-drift gate — this incident's post-mortem; scope: own-package npm-vs-main watcher) - skills/update: [1.87.0] example line; two oldest bullets trimmed to stay under the 20K session-load cap Cross-model release review: Codex xhigh (GPT-5.6 Sol), 3 rounds to CERTIFIED — caught a sed-falsified historical version citation and two unsupported duration claims in my own incident narrative. All suites green.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
hooks/model-effort-check.sh's model-aware floor andskills/sdlc/SKILL.md's removedeffort: maxfrontmatter both landed in v1.84.0./model opus-escalation half was never attempted.hooks/token-spike-check.sh(roadmap(#224-227): follow-ups from Codex review of auto-PRs #220) does adjacent but distinct post-hoc anomaly detection against past sessions, not the live Max-cap-aware monitor (e) originally asked for.No code, hooks, or live guidance changed — this is a documentation-only status correction to an internal tracking row.
Review history
Codex (GPT-5.6 Sol, xhigh) — 3 rounds to CERTIFIED, not rubber-stamped:
maxconfigs are silent (settings-onlymaxstill warns); (e)'s "zero hits" grep claim was false (the concept is discussed as manual guidance, just no automated detector). All 4 fixed.hooks/token-spike-check.sh(roadmap(#224-227): follow-ups from Codex review of auto-PRs #220) already does adjacent token-burn detection. Fixed by precisely distinguishing post-hoc anomaly detection from the live cap-aware monitor never built.Test plan
tests/test-doc-consistency.sh: 67/67 green throughout all 3 roundsgit diff --checkclean, diff scoped to only the API features to review (31 pending as of 2026-07-10) #434 row